home *** CD-ROM | disk | FTP | other *** search
- Path: vixen.cso.uiuc.edu!msaladin
- From: msaladin@students.uiuc.edu (Saladino Michael D)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: One hardware-basher's manifesto
- Date: 29 Feb 1996 23:13:06 GMT
- Organization: University of Illinois at Urbana
- Message-ID: <4h5bu2$fur@vixen.cso.uiuc.edu>
- References: <4ge8na$vhe@ar.ar.com.au> <08000305729070351637@BIRDLAND> <4guenp$1a1@vixen.cso.uiuc.edu> <4h51kg$cio@maureen.teleport.com>
- NNTP-Posting-Host: ux5.cso.uiuc.edu
-
- sschaem@teleport.com (Stephan Schaem) writes:
-
- > You do not ALWAYS access ram linearly... Drawing a vertical line in 32bit
- > color only accessing ram linearly?
-
- >.. move.l d0,(a0)
- > adda.l a1,a0
- > dbra d0,..
-
- > Since you are the expert here tell me what happen on a 030/040/060 with
- > this and burst on? is it really 10 time faster with the burst on?
-
- You're right, you don't always and I shouldn't have been so general.
- But, guess what? You do most of the time. What happens to all those
- variable references that would have been helped? What happens to all
- those horizontal lines, or do you just draw vertical ones? What happens
- to the other FORTY tasks running in the background? Or maybe you
- go around switching your burst mode on and off (a very time consuming
- change). You are trying to use one example of code that would run
- faster to create a rule. It's not true. You must take into account
- ALL of your code AND everyone elses that's also running on your system.
- Then, and only then, does turning burst mode off look stupid. Unless
- you are writing a program that takes over the machine and draws a demo
- animation in vertical strokes. And, boy do we need another one of those.
-